Great work on this, thanks for the effort! The Rust code is clean, 418 tests pass, and all existing commands work fine.

We have one architectural concern we'd like to discuss before merging.

The TypeScript plugin reimplements rewrite logic that should live in Rust.

hooks/opencode-rtk-plugin.ts is 309 lines of regex-based command rewriting — the same logic that exists in hooks/rtk-rewrite.sh (bash) and will soon be native Rust via PR #150 (rtk
hook-rewrite). This means rewrite logic maintained in 3 places, and the TS version already diverges (it rewrites cat, grep, find, diff which the bash hook intentionally skips because the
argument interfaces are incompatible).

Proposed architecture: rtk hook-rewrite as universal entry point

Once PR #150 merges, every integration should call the same Rust binary:

Claude Code → hook (JSON) → rtk hook-rewrite
OpenCode → plugin (TS) → rtk hook-rewrite
Gemini CLI → hook (bash) → rtk hook-rewrite
Codex → hook (TBD) → rtk hook-rewrite

OpenCode's tool.execute.before hook https://opencode.ai/docs/plugins/, so the plugin could be ~10 lines:
hooks: {
"tool.execute.before": async (input) => {
const result = await $rtk hook-rewrite ${input.command};
return { ...input, command: result.text() };
}
}

Single source of truth in Rust, zero divergence, trivial to add new providers.

Other notes:

• rtk discover --opencode silently returns zero results for all users — OpenCode uses SQLite but the provider only reads JSONL
• The rtk init --opencode installer and README docs are good and can be reused as-is

Suggestion: Wait for PR #150 to merge, then resubmit with a minimal plugin calling rtk hook-rewrite. We're open to discussing the approach — happy to help shape this!